Refactoring CQRS structure for enhanced clarity and accessibility #205
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
Previously, Commands, Queries, Handlers, and Validators were nested within a static class named after the command or query. For instance, the
CreateTenantCommand
static class included nestedCommand
,Handler
, andValidator
classes. This approach, while structured, led to references likeCreateTenant.Command
in the API, which received multiple remarks for its complexity and readability.Addressing these concerns, the nested classes have now been elevated to the top level and renamed accordingly. For example, what was previously
CreateTenant.Command
is nowCreateTenantCommand
.Checklist